-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix syncing total count when using signed_only=True #1609
Conversation
if cv_unique in self.already_synced: | ||
return | ||
|
||
# Mark the collection version as being processed | ||
self.already_synced.add(cv_unique) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this? Apart from eating a lot of memory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is for the dependency sync. We don't want to re-process the same collection version that we have already synced. There is only like 50,000 collection versions so this set grows up to a few megabytes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So it's for depsolving?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to skip this when doing a full mirror sync anyway?
What if we do a bloom filter thing?
(Just a few thoughts...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I added an if check for adding a CV to the already-synced set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, this was asking on a tangent. Would you mind making it a separate change?
f237538
to
dcfaec8
Compare
dcfaec8
to
3a0e03b
Compare
fixes: #1608
https://issues.redhat.com/browse/AAH-2692